About bcked
Mission
Support the movement towards asset-backed cryptocurrencies and tokenized real world assets (RWAs) by providing the definite information source on backing.
Motivation
How do you protect your hard earned money during a recession? What if fiat is inflating? What if the stock market is crashing? What if the housing bubble could burst at any time? What if your favorite crypto project is just hype without anything backing it up?
In the wake of the 2022 recession, I asked myself these questions. For me, some form of diversification into different asset classes seemed sensible. Also cryptocurrencies which are backed by another asset looked very interesting to me. Or even better, a cryptocurrency backed by other assets of different asset classes. While researching this topic, I quickly noticed the lack of information on backed cryptocurrencies. This is why I created this open-source project which seeks to build up a knowledge base and a community around the topic of cryptocurrency backing.
If you have any questions, want to contribute or any other request, feel free to write on GitHub or by email contact@bcked.com.
Roadmap
Last updated on 3/22/2023
We currently do not explicitly track who issued an asset. URLs to the project etc. are provided but the issuer is not named, nor explicitly tracked. Creating a profile per issuer would allow us to create an issuer view which can list all tracked assets of this issuer. For project offering multiple tokens of a specific asset class this could be a good way to give an overview over their issued assets.
- Restructure the asset data to reference a unique issuer ID
- Create
.ymlprofiles for every issuer with information like name and homepage - Provide an API endpoint for all issuers
- Create a new issuer view with the details and a list of all assets by this issuer
- Create an independent list of tracked issuers
- Link the issuer on the asset view
- Think about possible stats per issuer with respect to backing
Last updated on 3/22/2023
Chains are currently a second class citizen. For the chain of backing they actually play an important factor since assets might just be backed through multiple pegs from different issuers. This adds a significant risk factor which is currently not visualized.
- Add a view with all details about one chain/market
- On the asset view link the chain view
Last updated on 3/22/2023
Currently assets are aggregated over all chains they are on. This is planned to be changed. We then should visualize which chain or market an asset is on. Show a small icon on the lower right of the asset icon everywhere where an asset icon is displayed. Maybe using something like the circular avatar with bottom notification of Tailwind:

Last updated on 5/29/2023
Currently we do just show the backing tokens. It would be great to have an explainer (free text) which can contain information like how the backing mechanism works, important smart contracts, how one can redeem (or mint), or any other insightful detail. Put this at the bottom of the asset view.
Last updated on 1/17/2023
Currently the API is not documented and its availability is not visible. Go with a slate docs design as done in spenhouet.com/beautiful-docs and tailwindui.com/templates/protocol. Similar to the language switcher, show a response result switcher (200, 404). As good examples take a look at CoinMarketCap API Documentation and the Stripe API Documentation. If possible, make the query parameters changeable and dynamically load the new query results like done by Open API as in the example of DefiLlama.
Last updated on 1/17/2023
Currently, the list of underlying assets does not list the asset itself, if it is somehow used as backing itself. Having such a self-backing is a risk and we should try to visualize that. We should make sure that in case, the list of underlying assets and the list of derivatives also lists the asset itself. At some position we should show a warning that this asset also has self backing which is not included in the shown stats and the Sankey diagram.
Last updated on 1/12/2023
Currently we have a simple FAQ page which allows for short explainers of used terminology. We want to replace this by a blog like "Learn" page where we can add blog like articles explaining terms in an extended way on individual pages. This should also help with SEO. Use H1 headers for the blog article titles. For the Learn overview page, see if we can provide the respective JSON-LD for an FAQ site.
Last updated on 1/12/2023
Currently the discover section only shows three different groups and only the top 3 assets for the respective group. Add more groups using the carousel design pattern. One group addition should be "Latest Addition"/"New Listing" (or similar). Add a "show more" button to open a full list of this group.
Last updated on 1/12/2023
In case an asset has major issues we are aware of and should warn about, we should have the ability to just add a markdown file called
warning.mdto the asset folder for a banner showing the content on the asset view.Last updated on 1/12/2023
The backing history and backing distribution might be correlated or for any other reason a comparison between two assets might be of interest. Provide the possibility to compare two assets.
- Show a new view which overlays the backing history of both assets
- Show the backing tokens in a side by side view where the same tokens are in the same rows
Last updated on 1/12/2023
We started also mirroring records like attestations. It would be good to provide these through the asset view.
Last updated on 3/22/2023
Currently the backing history is shown as a line chart. Instead we could display a stacked area chart with all underlying assets. The total height is then the total backing. We should display a mouse pointer legend listing the value of the individual underlying assets at the timepoint of the mouse pointer (check mobile accessibility). Also list the total backing. Use the same line + fading area design as we currently use. For features take a look at the D3 stacked area chart. Use same time range selector as in D3 example. For an example look at the Collateral Breakdown chart of Dune.
Last updated on 1/15/2023
Currently the API tries to conform to REST (not even complete RESTful yet). It might be worth changing the data structure to follow the Financial Regulatory (FIRE) Data Standard. It's not clear if this is really applicable and useful for bcked API users.